Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@chat-frontend/src/api/fetchSidebarBuckets/index.ts`:
- Around line 50-56: The fetchSidebarBuckets API currently calls request(...)
with two args; update the function signature for fetchSidebarBuckets to accept
an optional opts parameter and pass that opts as the third argument to all three
request calls (the requests using subjects userSubscriptionGetCurrent and
userSubscriptionGetApps) so each request uses request(subject, payload, opts)
consistently; ensure the opts parameter is threaded through even when undefined
to match API/test conventions.
- Around line 50-57: The Promise.all call can throw away the successful
canonical payload (allResp) if either the favorites or apps requests reject;
change the logic to run the three requests with Promise.allSettled (or await
each with try/catch) so that userSubscriptionGetCurrent(user.account,
user.siteId) is preserved even when the other two fail, then map rejected
results for the favorite and apps calls to safe empty SidebarBucketReply
fallbacks and continue to use allResp to seed state.subscriptions and
channelDmIds; update references to allResp, favResp, and appResp accordingly so
only the failed auxiliaries are ignored rather than aborting the whole
bootstrap.

---

Outside diff comments:
In `@chat-frontend/src/components/MainApp/Sidebar/RoomList/RoomList.jsx`:
- Around line 47-53: The collapsible header currently uses a click-only div
(className "room-list-section-header") which is inaccessible; replace that div
with a semantic <button> (or React button element) inside RoomList.jsx and
attach the existing onClick handler (toggle(section.key)) to it, add
aria-expanded={isExpanded} (compute from your section state) and aria-controls
pointing to the collapsible region id, keep the chevron span
(aria-hidden="true") and the section.title inside the button, and remove any
custom keyboard handlers since a native button provides proper keyboard
semantics.

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@chat-frontend/src/api/fetchSidebarBuckets/index.ts`:
- Around line 34-42: The docblock is out of sync: it claims getCurrent({
favorite: true }) is fetched for Favorites but that code path is disabled;
update the comment around the bootstrap description to reflect the actual
runtime flow (only getCurrent() is fetched as the canonical subscription list
which seeds state.subscriptions and channelDmIds, and getApps() is fetched for
the Apps section) and note that Favorites are derived from state.subscriptions
at render time (or that favorite-specific fetching is intentionally disabled)
instead of claiming getCurrent({ favorite: true }) is called.
- Around line 75-79: Remove the temporary debug that logs full subscription
payloads: delete the console.log('[sidebar-bootstrap]', label, result.value)
call in the fetch/sidebar bootstrap code so that label and result.value are not
emitted to logs; keep the return result.value behavior unchanged, or if you need
retained diagnostics replace it with a sanitized/logger-guarded message (e.g.,
log only label or a redacted summary) using the existing logger instead of raw
console.log.

In `@chat-frontend/src/api/listRooms/index.ts`:
- Around line 10-11: Update the listRooms API to accept an optional opts
parameter and pass it through to the NATS request call: add an opts parameter to
the function signature where roomsList(user.account) / subject is created, and
call request<ListRoomsResponse>(subject, {}, opts) (three-argument form) instead
of the current two-argument call; ensure you preserve the payload shape and
types and thread opts through even when undefined to satisfy tests and coding
guidelines.
- Around line 12-16: Remove the temporary debug logging in the listRooms API
handler: delete the console.log call that prints '[sidebar-bootstrap]' along
with subject and resp (located in chat-frontend/src/api/listRooms/index.ts
inside the listRooms function or exported handler) so the full rooms response
payload is not logged; ensure no other leftover debug console.* calls remain and
return resp unchanged.

---

Duplicate comments:
In `@chat-frontend/src/api/fetchSidebarBuckets/index.ts`:
- Around line 65-67: Add an optional opts parameter to fetchSidebarBuckets and
thread it into the NATS requests: change the two-argument calls to
request(currentSubject, {}, opts) and request(appsSubject, {}, opts) (use the
three-argument request(subject, payload, opts) shape) so both Promise.allSettled
entries pass opts consistently; update the fetchSidebarBuckets signature to
accept opts (optional) and forward it to any other request(...) invocations in
that function.

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Duplicate comments:
In `@chat-frontend/src/api/fetchSidebarBuckets/index.ts`:
- Around line 76-81: Remove the temporary debug console.log that prints per-user
subscription payloads in the sidebar bootstrap path; locate the log call that
uses '[sidebar-bootstrap]', label and result.value.subscriptions (and the mapped
roomIds) inside the fetchSidebarBuckets flow and delete that statement, leaving
only existing error/failure logging in place so success paths no longer emit
payload-style logs.
- Around line 61-69: fetchSidebarBuckets currently uses the 2-arg request(...)
shape and doesn't accept opts; update the function signature
fetchSidebarBuckets({ user, request }: Nats, args?, opts?) to follow the
project's API contract and thread opts into each NATS call: replace
request<SidebarBucketReply>(favSubject, { favorite: true }) and the two other
request calls with the three-argument form
request<SidebarBucketReply>(favSubject, { favorite: true }, opts) (and likewise
for appsSubject and roomsSubject) and ensure Promise.allSettled still collects
those returned promises.